Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d5a6b74c2d3bb3b482540ce9b370f8ad800fd4fe3f052a1259966bbfc2db354a

Tx prefix hash: b5d1ab4780b40d31e7d31cd5286ddb6caec4a5e556cc5ba5ec8d2948ef6f7406
Tx public key: 058bf4612116f63c4b9dacb8cedadde13825385cc9fbcdf3e861f64bf5250d98
Timestamp: 1722234399 Timestamp [UCT]: 2024-07-29 06:26:39 Age [y:d:h:m:s]: 00:248:01:59:09
Block: 1076084 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177199 RingCT/type: yes/0
Extra: 01058bf4612116f63c4b9dacb8cedadde13825385cc9fbcdf3e861f64bf5250d98021100000010e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ece2973ac023fa2df00265dc1e815686b133eeb3742ff5881ae15de8cf5d3f7b 0.600000000000 1548619 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": 1076094, "vin": [ { "gen": { "height": 1076084 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ece2973ac023fa2df00265dc1e815686b133eeb3742ff5881ae15de8cf5d3f7b" } } ], "extra": [ 1, 5, 139, 244, 97, 33, 22, 246, 60, 75, 157, 172, 184, 206, 218, 221, 225, 56, 37, 56, 92, 201, 251, 205, 243, 232, 97, 246, 75, 245, 37, 13, 152, 2, 17, 0, 0, 0, 16, 233, 20, 221, 21, 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