Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d4d7fddd1d380f9aa682c61845ee8be7cc321b01823d67f905d53e8cd4e12002

Tx prefix hash: 7f04942b939b6efb680d72380837431dd448f27c7f97f1e8d348837a33f839df
Tx public key: 80e978d159aef4d6e7b067b9f8367fafe0516dfed18c65f85241cbf08021b35c
Timestamp: 1734194755 Timestamp [UCT]: 2024-12-14 16:45:55 Age [y:d:h:m:s]: 00:100:23:41:02
Block: 1175142 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 71944 RingCT/type: yes/0
Extra: 0180e978d159aef4d6e7b067b9f8367fafe0516dfed18c65f85241cbf08021b35c021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9902521217e50522bf33f90988cc33f36097eec8004d85a7509ad7a6346dc7b4 0.600000000000 1661381 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": 1175152, "vin": [ { "gen": { "height": 1175142 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9902521217e50522bf33f90988cc33f36097eec8004d85a7509ad7a6346dc7b4" } } ], "extra": [ 1, 128, 233, 120, 209, 89, 174, 244, 214, 231, 176, 103, 185, 248, 54, 127, 175, 224, 81, 109, 254, 209, 140, 101, 248, 82, 65, 203, 240, 128, 33, 179, 92, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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