Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5495f0d27d6337db5eaa89e91ca1d45a07af6f8ec5e7978a5498189e66f47e01

Tx prefix hash: a8b70e8e5788b010f9f3b9d70cfe98b9f5035c1f7a3e2a8618022bb201f0b82b
Tx public key: 0dbe6525e1d7817d14ababd70a03a1589c2209cdb19744fa3d898b025af9337c
Timestamp: 1731836070 Timestamp [UCT]: 2024-11-17 09:34:30 Age [y:d:h:m:s]: 00:139:23:56:48
Block: 1155586 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99877 RingCT/type: yes/0
Extra: 010dbe6525e1d7817d14ababd70a03a1589c2209cdb19744fa3d898b025af9337c021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3163be77af0f038e799db12e88e4189c82f2059e99b8263a5dbe9991380d5ee9 0.600000000000 1641203 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": 1155596, "vin": [ { "gen": { "height": 1155586 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3163be77af0f038e799db12e88e4189c82f2059e99b8263a5dbe9991380d5ee9" } } ], "extra": [ 1, 13, 190, 101, 37, 225, 215, 129, 125, 20, 171, 171, 215, 10, 3, 161, 88, 156, 34, 9, 205, 177, 151, 68, 250, 61, 137, 139, 2, 90, 249, 51, 124, 2, 17, 0, 0, 0, 3, 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