Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e232868a1c5204a3f788a93e661b99b4259d6a281ce11a83acb87a9228c61081

Tx prefix hash: 9616f5a0003c8eb9f0cf6d0f4029a304ec66061eb64a5f233931567f19aedc58
Tx public key: d5efa36bf585035416d6081edf2db9c9f26c4d673291aa63e8b207c0d0b10666
Timestamp: 1583080331 Timestamp [UCT]: 2020-03-01 16:32:11 Age [y:d:h:m:s]: 04:313:20:49:04
Block: 74610 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1118297 RingCT/type: yes/0
Extra: 01d5efa36bf585035416d6081edf2db9c9f26c4d673291aa63e8b207c0d0b1066602110000001b03d36d11000000000000000000

1 output(s) for total of 347.365670532000 dcy

stealth address amount amount idx
00: de78cc8fe283c42427c3714254019fbfd06533dae00ad18dd4a78a8f7f767042 347.365670532000 138036 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": 74620, "vin": [ { "gen": { "height": 74610 } } ], "vout": [ { "amount": 347365670532, "target": { "key": "de78cc8fe283c42427c3714254019fbfd06533dae00ad18dd4a78a8f7f767042" } } ], "extra": [ 1, 213, 239, 163, 107, 245, 133, 3, 84, 22, 214, 8, 30, 223, 45, 185, 201, 242, 108, 77, 103, 50, 145, 170, 99, 232, 178, 7, 192, 208, 177, 6, 102, 2, 17, 0, 0, 0, 27, 3, 211, 109, 17, 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