Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 58f8b1a682425957c3771b23a8066c45bc7a9c4fab7406e23cb52497e4515c64

Tx prefix hash: 472f4f0241eb0f126c96c60d4861fe897d3b2c350b3328a0845aff626020a19e
Tx public key: 5ae76c903ba0deeb7f5769baa4a5132ef82d4b52ecb4aca2fa188e31bb4f77bd
Timestamp: 1737510663 Timestamp [UCT]: 2025-01-22 01:51:03 Age [y:d:h:m:s]: 00:146:14:47:12
Block: 1202531 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104540 RingCT/type: yes/0
Extra: 015ae76c903ba0deeb7f5769baa4a5132ef82d4b52ecb4aca2fa188e31bb4f77bd0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 360f618cdad709d4ad621b96afb74a02a3d37200aacd44e242ef43619b8db9e9 0.600000000000 1689196 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": 1202541, "vin": [ { "gen": { "height": 1202531 } } ], "vout": [ { "amount": 600000000, "target": { "key": "360f618cdad709d4ad621b96afb74a02a3d37200aacd44e242ef43619b8db9e9" } } ], "extra": [ 1, 90, 231, 108, 144, 59, 160, 222, 235, 127, 87, 105, 186, 164, 165, 19, 46, 248, 45, 75, 82, 236, 180, 172, 162, 250, 24, 142, 49, 187, 79, 119, 189, 2, 17, 0, 0, 0, 3, 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