Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 24f5af4e903a84455dda608ce39460a78e50b7e7ad3909ae9bd2950bd2ea2717

Tx prefix hash: 6e118c6bfaaa1ed42cb4fdba97322f4ab8c778175be2b2d8fd6746d33c29d22b
Tx public key: 459e20e1ba1d318758b4348926c19f7eaeed3c952a2e3267f933587c59e25b70
Timestamp: 1721230196 Timestamp [UCT]: 2024-07-17 15:29:56 Age [y:d:h:m:s]: 00:219:20:17:58
Block: 1067764 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 156988 RingCT/type: yes/0
Extra: 01459e20e1ba1d318758b4348926c19f7eaeed3c952a2e3267f933587c59e25b70021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 59b8b6677a45e9cb265c08b1599e1fd71367961080bb4bd79dbe31edd91deaae 0.600000000000 1538667 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": 1067774, "vin": [ { "gen": { "height": 1067764 } } ], "vout": [ { "amount": 600000000, "target": { "key": "59b8b6677a45e9cb265c08b1599e1fd71367961080bb4bd79dbe31edd91deaae" } } ], "extra": [ 1, 69, 158, 32, 225, 186, 29, 49, 135, 88, 180, 52, 137, 38, 193, 159, 126, 174, 237, 60, 149, 42, 46, 50, 103, 249, 51, 88, 124, 89, 226, 91, 112, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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