Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ebaa43179666a209df7b8fec92608edb149b9fe2960f06b503617a1c7cd1390c

Tx prefix hash: 32fe2dae2c7fd98e8fce135a96d31c4e50eedeaa7ad6fb1a522e9b6872811b31
Tx public key: 57f604d54e1958d44733489d9e9d93b14b83068ccb4a0ccb78762468968d8841
Timestamp: 1719369437 Timestamp [UCT]: 2024-06-26 02:37:17 Age [y:d:h:m:s]: 00:356:01:36:55
Block: 1052311 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 254391 RingCT/type: yes/0
Extra: 0157f604d54e1958d44733489d9e9d93b14b83068ccb4a0ccb78762468968d88410211000000087a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5dacf2602daad15d617a2fb38dc668f0af9b0d05a5277161e7d8a9c2931d5f67 0.600000000000 1522634 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": 1052321, "vin": [ { "gen": { "height": 1052311 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5dacf2602daad15d617a2fb38dc668f0af9b0d05a5277161e7d8a9c2931d5f67" } } ], "extra": [ 1, 87, 246, 4, 213, 78, 25, 88, 212, 71, 51, 72, 157, 158, 157, 147, 177, 75, 131, 6, 140, 203, 74, 12, 203, 120, 118, 36, 104, 150, 141, 136, 65, 2, 17, 0, 0, 0, 8, 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