Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: db7b2d44f93a461f8483040de8ed04df47d954a17f23226e64a7c66bc854a63b

Tx prefix hash: 0c1c625b1bdb6c0728b880cb58c3b4c5ba3711567746c417dfc2b6e4dcceac52
Tx public key: 1240f644dd5084ab0ff0ae6ca3e832cb2faf71086ab421d34a1720eeecb678fe
Timestamp: 1673504908 Timestamp [UCT]: 2023-01-12 06:28:28 Age [y:d:h:m:s]: 02:051:20:50:41
Block: 672946 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 558730 RingCT/type: yes/0
Extra: 011240f644dd5084ab0ff0ae6ca3e832cb2faf71086ab421d34a1720eeecb678fe02110000000a8b7b6602000000000000000000

1 output(s) for total of 3.616183846000 dcy

stealth address amount amount idx
00: 9f0a4e514d9ed69a0ab67fd4debd9e42822da083d13c1d9ac0d63ce5e0fb570f 3.616183846000 1114517 of 0

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": 672956, "vin": [ { "gen": { "height": 672946 } } ], "vout": [ { "amount": 3616183846, "target": { "key": "9f0a4e514d9ed69a0ab67fd4debd9e42822da083d13c1d9ac0d63ce5e0fb570f" } } ], "extra": [ 1, 18, 64, 246, 68, 221, 80, 132, 171, 15, 240, 174, 108, 163, 232, 50, 203, 47, 175, 113, 8, 106, 180, 33, 211, 74, 23, 32, 238, 236, 182, 120, 254, 2, 17, 0, 0, 0, 10, 139, 123, 102, 2, 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