Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b96bb928cc9c2745f7dc701315e78ad92979ea5e40f14c272e9173bdfa7f50b9

Tx prefix hash: 6f91308a02d2f4864103e5d474af0ad8c9ff5b9abd3f8c59d4f51d31d78b49b4
Tx public key: bcc96f904f06867a7cabadd5a27c95c62a0a65b6d3d833f8acd7cda5a1ba693f
Timestamp: 1723126885 Timestamp [UCT]: 2024-08-08 14:21:25 Age [y:d:h:m:s]: 01:090:00:02:20
Block: 1083470 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 322787 RingCT/type: yes/0
Extra: 01bcc96f904f06867a7cabadd5a27c95c62a0a65b6d3d833f8acd7cda5a1ba693f02110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d446f8ffbc1a54055d08751679c1810e0f20496047997af4e2b8c8404859cbb1 0.600000000000 1557405 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": 1083480, "vin": [ { "gen": { "height": 1083470 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d446f8ffbc1a54055d08751679c1810e0f20496047997af4e2b8c8404859cbb1" } } ], "extra": [ 1, 188, 201, 111, 144, 79, 6, 134, 122, 124, 171, 173, 213, 162, 124, 149, 198, 42, 10, 101, 182, 211, 216, 51, 248, 172, 215, 205, 165, 161, 186, 105, 63, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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