Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed61f91a943756d52a1f96996ff20760487873cb90d1ff1cea4f5bf058ebf0d8

Tx prefix hash: 152fcafd59f1afeb21226045481ce0b8b545e17ea1ecd2402ec5d6be937f5a43
Tx public key: eaba09e7cb3b76aaef6e67353cff00c6ffabe5cb96655299f40ff0c0e4558cbf
Timestamp: 1715058759 Timestamp [UCT]: 2024-05-07 05:12:39 Age [y:d:h:m:s]: 01:007:02:31:06
Block: 1016595 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 266004 RingCT/type: yes/0
Extra: 01eaba09e7cb3b76aaef6e67353cff00c6ffabe5cb96655299f40ff0c0e4558cbf0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 45c6dcfcbae34832f582a38ec991f258e7943ec4e2beda3c8717a4e8d885a1f4 0.600000000000 1480220 of 15

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": 1016605, "vin": [ { "gen": { "height": 1016595 } } ], "vout": [ { "amount": 600000000, "target": { "key": "45c6dcfcbae34832f582a38ec991f258e7943ec4e2beda3c8717a4e8d885a1f4" } } ], "extra": [ 1, 234, 186, 9, 231, 203, 59, 118, 170, 239, 110, 103, 53, 60, 255, 0, 198, 255, 171, 229, 203, 150, 101, 82, 153, 244, 15, 240, 192, 228, 85, 140, 191, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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