Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bd147bb6d679d95010a7bd5ba57969cf3778fcd63b5fa5ccc0dffc32d4e5e926

Tx prefix hash: 89576113c4421117bee94282833b8430e1fa784066209b3c2db146562f45c4e7
Tx public key: 63425cdb17ab81ec9b9bde4c24f737cf849b962d5a0dc41a7685419cf84a2a31
Timestamp: 1640150903 Timestamp [UCT]: 2021-12-22 05:28:23 Age [y:d:h:m:s]: 03:019:16:56:15
Block: 400838 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 793055 RingCT/type: yes/0
Extra: 0163425cdb17ab81ec9b9bde4c24f737cf849b962d5a0dc41a7685419cf84a2a310211000000027659c797000000000000000000

1 output(s) for total of 28.836934196000 dcy

stealth address amount amount idx
00: 36b038c7ff2ccc9f9484b674a7ae9e81aa8504436676af9f4086ccb04c9c5964 28.836934196000 800321 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": 400848, "vin": [ { "gen": { "height": 400838 } } ], "vout": [ { "amount": 28836934196, "target": { "key": "36b038c7ff2ccc9f9484b674a7ae9e81aa8504436676af9f4086ccb04c9c5964" } } ], "extra": [ 1, 99, 66, 92, 219, 23, 171, 129, 236, 155, 155, 222, 76, 36, 247, 55, 207, 132, 155, 150, 45, 90, 13, 196, 26, 118, 133, 65, 156, 248, 74, 42, 49, 2, 17, 0, 0, 0, 2, 118, 89, 199, 151, 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