Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 85f2e97ded8403d163e11313efeab352641e446a6a5d9b185ccfb5f2d32f0bf8

Tx prefix hash: 3ebd14be0eded0b2b84ae952f400996777ed356abb68ad72643bee26fa1fba0c
Tx public key: e9e12e3f445769ef34685139468e33b3ce4b3e2a95ebb93840f9a13c4fccb2db
Timestamp: 1733245875 Timestamp [UCT]: 2024-12-03 17:11:15 Age [y:d:h:m:s]: 00:115:19:24:23
Block: 1167272 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 82565 RingCT/type: yes/0
Extra: 01e9e12e3f445769ef34685139468e33b3ce4b3e2a95ebb93840f9a13c4fccb2db0211000000081f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 34014afa1a3477acbf5c8b87f46c040f6fcee31fe6af6f16b94eaff198b0bb82 0.600000000000 1652967 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": 1167282, "vin": [ { "gen": { "height": 1167272 } } ], "vout": [ { "amount": 600000000, "target": { "key": "34014afa1a3477acbf5c8b87f46c040f6fcee31fe6af6f16b94eaff198b0bb82" } } ], "extra": [ 1, 233, 225, 46, 63, 68, 87, 105, 239, 52, 104, 81, 57, 70, 142, 51, 179, 206, 75, 62, 42, 149, 235, 185, 56, 64, 249, 161, 60, 79, 204, 178, 219, 2, 17, 0, 0, 0, 8, 31, 10, 83, 235, 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