Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0767afb8d6b56a6261dae0cb2c7a6c8ec64ec6f32d13abbbe1a0b62460d5a4ea

Tx prefix hash: 3e30d79c999384f36fcd037c4d465218abd20f536dd1107f8b4e0e3ac1e65775
Tx public key: 4860b1d2bd791a81ac63fb28e8239ad2e2f555b062479ad496eebf58285ee52a
Timestamp: 1723662007 Timestamp [UCT]: 2024-08-14 19:00:07 Age [y:d:h:m:s]: 00:142:15:14:34
Block: 1087920 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102041 RingCT/type: yes/0
Extra: 014860b1d2bd791a81ac63fb28e8239ad2e2f555b062479ad496eebf58285ee52a021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eb3f24368cff4a4a597d3c4f9a3cfd1e51cd54c09d06412abe949ef3339a1a37 0.600000000000 1562531 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": 1087930, "vin": [ { "gen": { "height": 1087920 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eb3f24368cff4a4a597d3c4f9a3cfd1e51cd54c09d06412abe949ef3339a1a37" } } ], "extra": [ 1, 72, 96, 177, 210, 189, 121, 26, 129, 172, 99, 251, 40, 232, 35, 154, 210, 226, 245, 85, 176, 98, 71, 154, 212, 150, 238, 191, 88, 40, 94, 229, 42, 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