Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0d7ab3be24433ebfd811fb2932fd4757cd9e19e3a72f0b30e8f5ef86cc505dd1

Tx prefix hash: 261715d12c4c89a4d72dd97f325c919855e598bcc89ea4ceef2aec06dc6f2646
Tx public key: 34e748ad0a0d85f61b7fe97fa21afec91ed3853854e81d43e7814444eab116d7
Timestamp: 1583077683 Timestamp [UCT]: 2020-03-01 15:48:03 Age [y:d:h:m:s]: 04:259:11:55:13
Block: 74519 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1079458 RingCT/type: yes/0
Extra: 0134e748ad0a0d85f61b7fe97fa21afec91ed3853854e81d43e7814444eab116d702110000022956c366d3000000000000000000

1 output(s) for total of 347.691502457000 dcy

stealth address amount amount idx
00: dbe460136f87557adf0c309862b9df01d37eb20455102baa7087c658481f83b9 347.691502457000 137894 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": 74529, "vin": [ { "gen": { "height": 74519 } } ], "vout": [ { "amount": 347691502457, "target": { "key": "dbe460136f87557adf0c309862b9df01d37eb20455102baa7087c658481f83b9" } } ], "extra": [ 1, 52, 231, 72, 173, 10, 13, 133, 246, 27, 127, 233, 127, 162, 26, 254, 201, 30, 211, 133, 56, 84, 232, 29, 67, 231, 129, 68, 68, 234, 177, 22, 215, 2, 17, 0, 0, 2, 41, 86, 195, 102, 211, 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