Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a96240639fb8a276578d35f8c458177e5f5b103a132f1d5323504c3caad81c92

Tx prefix hash: 2b741ad621dc6fb19d856204daafe48b98aa74509bfa4f9d65e2a89f03639d1a
Tx public key: 1952a7139a9b89e7f68080a7416f231eb6523fb200da81d56ae7dab1c72ab11c
Timestamp: 1709447807 Timestamp [UCT]: 2024-03-03 06:36:47 Age [y:d:h:m:s]: 01:294:09:04:08
Block: 970073 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 469164 RingCT/type: yes/0
Extra: 011952a7139a9b89e7f68080a7416f231eb6523fb200da81d56ae7dab1c72ab11c0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 09fd074723af68daf65960809bc7f8c99f3859500caf5b2576a28df95bea0dfb 0.600000000000 1429922 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": 970083, "vin": [ { "gen": { "height": 970073 } } ], "vout": [ { "amount": 600000000, "target": { "key": "09fd074723af68daf65960809bc7f8c99f3859500caf5b2576a28df95bea0dfb" } } ], "extra": [ 1, 25, 82, 167, 19, 154, 155, 137, 231, 246, 128, 128, 167, 65, 111, 35, 30, 182, 82, 63, 178, 0, 218, 129, 213, 106, 231, 218, 177, 199, 42, 177, 28, 2, 17, 0, 0, 0, 2, 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