Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 45bd425a124149c18c37871fa12ef9336303957686d0baf1d09e86e81f054688

Tx prefix hash: 81ceea2f9f1eb21465e972a34770981d393c56410fa6e52cd405988424435a50
Tx public key: 9634eaa7df6ecff0eefc2b3d778d3b93d68578b75da97b0e00abb18d423f24a2
Timestamp: 1726489769 Timestamp [UCT]: 2024-09-16 12:29:29 Age [y:d:h:m:s]: 00:262:13:20:31
Block: 1111359 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187514 RingCT/type: yes/0
Extra: 019634eaa7df6ecff0eefc2b3d778d3b93d68578b75da97b0e00abb18d423f24a2021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 04d56e5b2729f7654b3a2d42f5044c40edc4b904291964d9d9fd3d76f36df811 0.600000000000 1590290 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": 1111369, "vin": [ { "gen": { "height": 1111359 } } ], "vout": [ { "amount": 600000000, "target": { "key": "04d56e5b2729f7654b3a2d42f5044c40edc4b904291964d9d9fd3d76f36df811" } } ], "extra": [ 1, 150, 52, 234, 167, 223, 110, 207, 240, 238, 252, 43, 61, 119, 141, 59, 147, 214, 133, 120, 183, 93, 169, 123, 14, 0, 171, 177, 141, 66, 63, 36, 162, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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