Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b04f085e5581b68389cb6406e0725bf1fd36c0ff45b9484f82b0fca7426e9e5d

Tx prefix hash: 3acbbc9ed654b051557dcde9d106ea1bad97cc132ed10cb8fafcc5d9129c991e
Tx public key: 8208cdf5f789c1266f628ed4e086d6d995e39e484fb6cb8d3b053da8a02e2c2e
Timestamp: 1736364060 Timestamp [UCT]: 2025-01-08 19:21:00 Age [y:d:h:m:s]: 00:077:15:32:14
Block: 1193079 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 55262 RingCT/type: yes/0
Extra: 018208cdf5f789c1266f628ed4e086d6d995e39e484fb6cb8d3b053da8a02e2c2e02110000000c007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5d44cb8e84337f09f6d9ce0d73505b06c092d4109734429ecb1a016eecd3abac 0.600000000000 1679638 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": 1193089, "vin": [ { "gen": { "height": 1193079 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5d44cb8e84337f09f6d9ce0d73505b06c092d4109734429ecb1a016eecd3abac" } } ], "extra": [ 1, 130, 8, 205, 245, 247, 137, 193, 38, 111, 98, 142, 212, 224, 134, 214, 217, 149, 227, 158, 72, 79, 182, 203, 141, 59, 5, 61, 168, 160, 46, 44, 46, 2, 17, 0, 0, 0, 12, 0, 127, 151, 138, 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