Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6724db4a8c5cc8a99240f87ac4509461469a09da7b8fbd57f5fa0a50744cfdc6

Tx prefix hash: 77ca286e1cb20534433727f7928a8f9e1f4979fd673f3262ca9a7fd85a540ab4
Tx public key: fe40da869f826cc040e1295938a1849403e9c4af9d3a4ce4d9c97a588e7b8bb3
Timestamp: 1704719186 Timestamp [UCT]: 2024-01-08 13:06:26 Age [y:d:h:m:s]: 01:310:07:47:27
Block: 930851 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 480626 RingCT/type: yes/0
Extra: 01fe40da869f826cc040e1295938a1849403e9c4af9d3a4ce4d9c97a588e7b8bb302110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ed95d2e6f811b891dae29e6178b1462af79d0928c9f83565474220d71b3cc009 0.600000000000 1388741 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": 930861, "vin": [ { "gen": { "height": 930851 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ed95d2e6f811b891dae29e6178b1462af79d0928c9f83565474220d71b3cc009" } } ], "extra": [ 1, 254, 64, 218, 134, 159, 130, 108, 192, 64, 225, 41, 89, 56, 161, 132, 148, 3, 233, 196, 175, 157, 58, 76, 228, 217, 201, 122, 88, 142, 123, 139, 179, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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