Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3d3c7e6cac3cea749f8d0250cd92cd0cf0bf5cb8412a0d33c40ff728c61e1fc5

Tx prefix hash: 9942e2b5ca4cf64c8981627a4d4929306d013ec6391739313e3a01b26c30a4da
Tx public key: c36aa5df9818bd132aff9fdea414b2b4b51143a010b384765be83cf295734a51
Timestamp: 1709447125 Timestamp [UCT]: 2024-03-03 06:25:25 Age [y:d:h:m:s]: 01:072:19:49:10
Block: 970068 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 313078 RingCT/type: yes/0
Extra: 01c36aa5df9818bd132aff9fdea414b2b4b51143a010b384765be83cf295734a510211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ecdd2e7c9a9570f836f8d13f006ced3a6d7b84c76aba8e72b7cdc4830c3af8e4 0.600000000000 1429917 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": 970078, "vin": [ { "gen": { "height": 970068 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ecdd2e7c9a9570f836f8d13f006ced3a6d7b84c76aba8e72b7cdc4830c3af8e4" } } ], "extra": [ 1, 195, 106, 165, 223, 152, 24, 189, 19, 42, 255, 159, 222, 164, 20, 178, 180, 181, 17, 67, 160, 16, 179, 132, 118, 91, 232, 60, 242, 149, 115, 74, 81, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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