Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa37e5237bf0870f44d267e90e8e71a284cc17f3e661f23ea0d74c59aeb0aaeb

Tx prefix hash: fe0a8a4e4926861f229e5fdad572c5a8730f535f973a9a7e6cc174e1a8a65401
Tx public key: 4b2a24b0f01204442e94e902590afff1ee6163c1d44a6630dc1b671f614e0753
Timestamp: 1658927551 Timestamp [UCT]: 2022-07-27 13:12:31 Age [y:d:h:m:s]: 02:271:03:58:26
Block: 552849 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 714999 RingCT/type: yes/0
Extra: 014b2a24b0f01204442e94e902590afff1ee6163c1d44a6630dc1b671f614e075302110000000cec6d1a1a000000000000000000

1 output(s) for total of 9.040280223000 dcy

stealth address amount amount idx
00: bdf0562450b4b229f680b19689fa42b3cfd850cb3171625dc5a993730a28ae73 9.040280223000 984605 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": 552859, "vin": [ { "gen": { "height": 552849 } } ], "vout": [ { "amount": 9040280223, "target": { "key": "bdf0562450b4b229f680b19689fa42b3cfd850cb3171625dc5a993730a28ae73" } } ], "extra": [ 1, 75, 42, 36, 176, 240, 18, 4, 68, 46, 148, 233, 2, 89, 10, 255, 241, 238, 97, 99, 193, 212, 74, 102, 48, 220, 27, 103, 31, 97, 78, 7, 83, 2, 17, 0, 0, 0, 12, 236, 109, 26, 26, 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