Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f5db3c6b2e27f5eb07eac6ad1c5f778c5d526239e465a248f768330d3060728f

Tx prefix hash: 1117e0d7dc5cf112959b66b6bf074c4a53b782b9f8e6db9a315233d544abfc7b
Tx public key: e12bbd8b2ce58710581e05c27e274390eb35d21bc19e999d0046b17aa2e8815c
Timestamp: 1718281066 Timestamp [UCT]: 2024-06-13 12:17:46 Age [y:d:h:m:s]: 00:275:11:03:30
Block: 1043304 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 196870 RingCT/type: yes/0
Extra: 01e12bbd8b2ce58710581e05c27e274390eb35d21bc19e999d0046b17aa2e8815c02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5618d532f069a7227cb2fd9295685aaf873bff03f813030f961c89eb72575c95 0.600000000000 1512425 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": 1043314, "vin": [ { "gen": { "height": 1043304 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5618d532f069a7227cb2fd9295685aaf873bff03f813030f961c89eb72575c95" } } ], "extra": [ 1, 225, 43, 189, 139, 44, 229, 135, 16, 88, 30, 5, 194, 126, 39, 67, 144, 235, 53, 210, 27, 193, 158, 153, 157, 0, 70, 177, 122, 162, 232, 129, 92, 2, 17, 0, 0, 0, 2, 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