Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d9891ea7d6921f953044f517c84965eb1325d9dcde901337c11dc14f1696104e

Tx prefix hash: b59d9793a452cfab76707d072041792f4969b1d9586cdb158f12fd8119bffe2c
Tx public key: cfb1927ebe83257cf8fa8e7d0f484911dffb235b32c699a2c4e732b803f63a5b
Timestamp: 1736313225 Timestamp [UCT]: 2025-01-08 05:13:45 Age [y:d:h:m:s]: 00:347:00:07:01
Block: 1192658 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 245567 RingCT/type: yes/0
Extra: 01cfb1927ebe83257cf8fa8e7d0f484911dffb235b32c699a2c4e732b803f63a5b02110000000b1f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2f70075194fe07dccfa7106959c2a66450da0bf142c60521b60e410afaff05a3 0.600000000000 1679213 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": 1192668, "vin": [ { "gen": { "height": 1192658 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f70075194fe07dccfa7106959c2a66450da0bf142c60521b60e410afaff05a3" } } ], "extra": [ 1, 207, 177, 146, 126, 190, 131, 37, 124, 248, 250, 142, 125, 15, 72, 73, 17, 223, 251, 35, 91, 50, 198, 153, 162, 196, 231, 50, 184, 3, 246, 58, 91, 2, 17, 0, 0, 0, 11, 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