Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2158f7d125e0fb95d1eb47ae1419e71898c0cc4fd688dda42084913e78e36608

Tx prefix hash: 7b4db5909c83303d4e0da9e43ff28d5c6eee3e55950b55d1a6d555c8c5ca9759
Tx public key: f1b15cd206987d0e8d726c6f3dfeadb85b85f5f826abf3e7bbb86ba3b2570be8
Timestamp: 1703747277 Timestamp [UCT]: 2023-12-28 07:07:57 Age [y:d:h:m:s]: 01:112:07:27:25
Block: 922820 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 341385 RingCT/type: yes/0
Extra: 01f1b15cd206987d0e8d726c6f3dfeadb85b85f5f826abf3e7bbb86ba3b2570be802110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e0aae6ce9d30ed8ed8618fe6deea89d2c88945b18ab5016f5f23ec19ce06e4e2 0.600000000000 1380524 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": 922830, "vin": [ { "gen": { "height": 922820 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e0aae6ce9d30ed8ed8618fe6deea89d2c88945b18ab5016f5f23ec19ce06e4e2" } } ], "extra": [ 1, 241, 177, 92, 210, 6, 152, 125, 14, 141, 114, 108, 111, 61, 254, 173, 184, 91, 133, 245, 248, 38, 171, 243, 231, 187, 184, 107, 163, 178, 87, 11, 232, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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