Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00353fd3fa8f2a43928a0ab104b03aaa48b17e6534e02f5daefdd341e1c4c625

Tx prefix hash: db8a8b63935c3944efe717ee679e57c59d934044462aaaf98a1e4a4dcb852fe5
Tx public key: 6b59e14d7f4d5dbacbc5f705a155c808cba2076f9164939bb74435754720c4ed
Timestamp: 1712649861 Timestamp [UCT]: 2024-04-09 08:04:21 Age [y:d:h:m:s]: 01:021:15:49:00
Block: 996593 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 276464 RingCT/type: yes/0
Extra: 016b59e14d7f4d5dbacbc5f705a155c808cba2076f9164939bb74435754720c4ed02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 80116eb380f6bf2fd06c2f979178d6d87d91edc1a6e35f763ed8d89f1cdee5f5 0.600000000000 1457015 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": 996603, "vin": [ { "gen": { "height": 996593 } } ], "vout": [ { "amount": 600000000, "target": { "key": "80116eb380f6bf2fd06c2f979178d6d87d91edc1a6e35f763ed8d89f1cdee5f5" } } ], "extra": [ 1, 107, 89, 225, 77, 127, 77, 93, 186, 203, 197, 247, 5, 161, 85, 200, 8, 203, 162, 7, 111, 145, 100, 147, 155, 183, 68, 53, 117, 71, 32, 196, 237, 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