Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b088130ab1cb5ad9c8b59f77c75a49432aeae8c4b6e995a653c60df6b0a91fe

Tx prefix hash: 0d2739279d4094ae2c7a42eb07502b264230e5130fe578bf692370db3b6a2d71
Tx public key: edde6687e2f854bba505041d20fd3b288e03d101ee8cf9772b47239865a92853
Timestamp: 1713918331 Timestamp [UCT]: 2024-04-24 00:25:31 Age [y:d:h:m:s]: 00:285:16:26:25
Block: 1007132 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 204197 RingCT/type: yes/0
Extra: 01edde6687e2f854bba505041d20fd3b288e03d101ee8cf9772b47239865a928530211000000177a9cf4c7000000000000000000

1 output(s) for total of 0.615610000000 dcy

stealth address amount amount idx
00: 48ef78ece8b99db4a1cb26c947b4d2afc4a0c47346657ab8ac93508bdfc47c0e 0.615610000000 1468374 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": 1007142, "vin": [ { "gen": { "height": 1007132 } } ], "vout": [ { "amount": 615610000, "target": { "key": "48ef78ece8b99db4a1cb26c947b4d2afc4a0c47346657ab8ac93508bdfc47c0e" } } ], "extra": [ 1, 237, 222, 102, 135, 226, 248, 84, 187, 165, 5, 4, 29, 32, 253, 59, 40, 142, 3, 209, 1, 238, 140, 249, 119, 43, 71, 35, 152, 101, 169, 40, 83, 2, 17, 0, 0, 0, 23, 122, 156, 244, 199, 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