Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 625a23ac6c9cf4f5aa95efe405919b267d558872d3d610fa339d8f4680b9d036

Tx prefix hash: a204964e3a0ff2e166308735d00bff85cdfc13a5115fd1ae8c020ecccc8ac2e2
Tx public key: ce64406ad8c674431e57c82a9206c36c8e3535912669bd478723c9c3d8a1a8ac
Timestamp: 1732019511 Timestamp [UCT]: 2024-11-19 12:31:51 Age [y:d:h:m:s]: 00:141:19:12:00
Block: 1157112 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101163 RingCT/type: yes/0
Extra: 01ce64406ad8c674431e57c82a9206c36c8e3535912669bd478723c9c3d8a1a8ac0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a13c102619ef42caea2d90b386c9fecb020025d8cf13f210f1a5f656e547e406 0.600000000000 1642735 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": 1157122, "vin": [ { "gen": { "height": 1157112 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a13c102619ef42caea2d90b386c9fecb020025d8cf13f210f1a5f656e547e406" } } ], "extra": [ 1, 206, 100, 64, 106, 216, 198, 116, 67, 30, 87, 200, 42, 146, 6, 195, 108, 142, 53, 53, 145, 38, 105, 189, 71, 135, 35, 201, 195, 216, 161, 168, 172, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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