Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae091e9f68c3041fe5ce838758e3694a080fc836ae1f3316592073b88c501d8f

Tx prefix hash: 6f72f3171e46129085fd1e45365080e2e30df5baa7d4640c26df66bcd135971b
Tx public key: a649be39ca8e20c586c3815c2d198b592da1e187d55522daf6d836b9a1aa6638
Timestamp: 1672684707 Timestamp [UCT]: 2023-01-02 18:38:27 Age [y:d:h:m:s]: 02:102:11:24:00
Block: 666158 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 594942 RingCT/type: yes/0
Extra: 01a649be39ca8e20c586c3815c2d198b592da1e187d55522daf6d836b9a1aa663802110000000352542ceb000000000000000000

1 output(s) for total of 3.808394888000 dcy

stealth address amount amount idx
00: bf86f248a0365d8e379f198af1603b02b4b9757d791515fe35df684ef93c8365 3.808394888000 1107257 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": 666168, "vin": [ { "gen": { "height": 666158 } } ], "vout": [ { "amount": 3808394888, "target": { "key": "bf86f248a0365d8e379f198af1603b02b4b9757d791515fe35df684ef93c8365" } } ], "extra": [ 1, 166, 73, 190, 57, 202, 142, 32, 197, 134, 195, 129, 92, 45, 25, 139, 89, 45, 161, 225, 135, 213, 85, 34, 218, 246, 216, 54, 185, 161, 170, 102, 56, 2, 17, 0, 0, 0, 3, 82, 84, 44, 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