Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 2abf23d03c2686cab407f62f2b0b836b7365c918737231226bae1ed17c999a63

Tx prefix hash: 8731c466228fa78689e1e12ea98487fe9e15bd711072c86f8d0c42a678f0d6f1
Tx public key: 0a1275d96ffb21dc97cc073768147ab35774c43ab2f4b3edf637222168e6887a
Timestamp: 1585240354 Timestamp [UCT]: 2020-03-26 16:32:34 Age [y:d:h:m:s]: 04:275:12:19:13
Block: 88068 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1095299 RingCT/type: yes/0
Extra: 010a1275d96ffb21dc97cc073768147ab35774c43ab2f4b3edf637222168e6887a02110000037b209b4bc8000000000000000000

1 output(s) for total of 313.469243176000 dcy

stealth address amount amount idx
00: f9e4ab6d5ea3383be36f4f8fa076aa692b98676490deb539582765879a704a64 313.469243176000 158564 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 88078, "vin": [ { "gen": { "height": 88068 } } ], "vout": [ { "amount": 313469243176, "target": { "key": "f9e4ab6d5ea3383be36f4f8fa076aa692b98676490deb539582765879a704a64" } } ], "extra": [ 1, 10, 18, 117, 217, 111, 251, 33, 220, 151, 204, 7, 55, 104, 20, 122, 179, 87, 116, 196, 58, 178, 244, 179, 237, 246, 55, 34, 33, 104, 230, 136, 122, 2, 17, 0, 0, 3, 123, 32, 155, 75, 200, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8