Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 17bd0da509526c33757dc43f6cf8ab8d4b6e03e75b9fe35fd55a112df901a85f

Tx prefix hash: 7f47a14ce5001ac18d46ffff21811bba5c4281fda6e1ba6aa4fdc0d6f67e6de7
Tx public key: 3aed7e368f9bf3c7b092dfc365ec13d7c3107c946728f502dbfc2120a06412ae
Timestamp: 1635969733 Timestamp [UCT]: 2021-11-03 20:02:13 Age [y:d:h:m:s]: 03:075:00:57:45
Block: 366686 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 832165 RingCT/type: yes/0
Extra: 013aed7e368f9bf3c7b092dfc365ec13d7c3107c946728f502dbfc2120a06412ae0211000000054a0f5013000000000000000000

1 output(s) for total of 37.418003119000 dcy

stealth address amount amount idx
00: bf18c71a4553394cb433606ed6a1b4bf50400fc940b2e0a66abf3de927672335 37.418003119000 744266 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": 366696, "vin": [ { "gen": { "height": 366686 } } ], "vout": [ { "amount": 37418003119, "target": { "key": "bf18c71a4553394cb433606ed6a1b4bf50400fc940b2e0a66abf3de927672335" } } ], "extra": [ 1, 58, 237, 126, 54, 143, 155, 243, 199, 176, 146, 223, 195, 101, 236, 19, 215, 195, 16, 124, 148, 103, 40, 245, 2, 219, 252, 33, 32, 160, 100, 18, 174, 2, 17, 0, 0, 0, 5, 74, 15, 80, 19, 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