Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c8b8e54b566fbaea850403f8683e63f5081bce0613c2389874080ebc7ed4c04b

Tx prefix hash: 7e43f6f793d1f4895696fbea3b38594c6e6794ee2ad1d63264caa7b5a7d74596
Tx public key: 56860922cec91a7d570e88503a16aa5369f7980dea90da693a6201cf6b9c237a
Timestamp: 1716307202 Timestamp [UCT]: 2024-05-21 16:00:02 Age [y:d:h:m:s]: 00:187:17:35:03
Block: 1026950 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 134364 RingCT/type: yes/0
Extra: 0156860922cec91a7d570e88503a16aa5369f7980dea90da693a6201cf6b9c237a0211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bd64b9a945e2ad0b4e154c75c4c199dfde224a4de32bbdb48e3f974171d93632 0.600000000000 1494313 of 15

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": 1026960, "vin": [ { "gen": { "height": 1026950 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bd64b9a945e2ad0b4e154c75c4c199dfde224a4de32bbdb48e3f974171d93632" } } ], "extra": [ 1, 86, 134, 9, 34, 206, 201, 26, 125, 87, 14, 136, 80, 58, 22, 170, 83, 105, 247, 152, 13, 234, 144, 218, 105, 58, 98, 1, 207, 107, 156, 35, 122, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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