Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 29ba1a724f9b788daa2bde014a1e267e1d9cf3d4be2fd90196c4f706a9383961

Tx prefix hash: e89cc06200e408fe20442f7092531b0bf1f5016a507c78a40b50aa11c1c51c38
Tx public key: 4a9f6ca636f0b1857bc5440d530218280a13c9a817fd8a4d4c1f28e58489221e
Timestamp: 1644277662 Timestamp [UCT]: 2022-02-07 23:47:42 Age [y:d:h:m:s]: 02:285:02:44:51
Block: 434123 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 722693 RingCT/type: yes/0
Extra: 014a9f6ca636f0b1857bc5440d530218280a13c9a817fd8a4d4c1f28e58489221e021100000019a8c141c5000000000000000000

1 output(s) for total of 22.365086901000 dcy

stealth address amount amount idx
00: 8fc5985c97f0a52867076b9e6acd43d8827a6753cb4772da7f1533494301f0e0 22.365086901000 845004 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": 434133, "vin": [ { "gen": { "height": 434123 } } ], "vout": [ { "amount": 22365086901, "target": { "key": "8fc5985c97f0a52867076b9e6acd43d8827a6753cb4772da7f1533494301f0e0" } } ], "extra": [ 1, 74, 159, 108, 166, 54, 240, 177, 133, 123, 197, 68, 13, 83, 2, 24, 40, 10, 19, 201, 168, 23, 253, 138, 77, 76, 31, 40, 229, 132, 137, 34, 30, 2, 17, 0, 0, 0, 25, 168, 193, 65, 197, 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