Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 01a164d0031dd30e879a6622e1584bc60f6102a169d3cb99f861872efe534b3b

Tx prefix hash: 004d5fde683032689736b2c9c3f0e460f29e97ba57cc47623d79cea26874d02d
Tx public key: fd0abf061084102ce4ede52b3320ce8cab758cd7b48db34d432bef2aba7d1a61
Timestamp: 1578200242 Timestamp [UCT]: 2020-01-05 04:57:22 Age [y:d:h:m:s]: 04:330:09:22:57
Block: 38975 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1125355 RingCT/type: yes/0
Extra: 01fd0abf061084102ce4ede52b3320ce8cab758cd7b48db34d432bef2aba7d1a6102110000000d4ac5aa02000000000000000000

1 output(s) for total of 455.890450161000 dcy

stealth address amount amount idx
00: bb280154268150488d8d8d320a991bef4869e381e3afae761ea69d27823d9dc0 455.890450161000 66846 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": 38985, "vin": [ { "gen": { "height": 38975 } } ], "vout": [ { "amount": 455890450161, "target": { "key": "bb280154268150488d8d8d320a991bef4869e381e3afae761ea69d27823d9dc0" } } ], "extra": [ 1, 253, 10, 191, 6, 16, 132, 16, 44, 228, 237, 229, 43, 51, 32, 206, 140, 171, 117, 140, 215, 180, 141, 179, 77, 67, 43, 239, 42, 186, 125, 26, 97, 2, 17, 0, 0, 0, 13, 74, 197, 170, 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