Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a6df478f9fafcc7d039ebdb1fbd3eeea7622b75d12a36220ebec0beabf7fbfe9

Tx prefix hash: 11995248a69e799925ae5bca25b3a4606e8089dfc351b3b3ebe8dfeb57826cd8
Tx public key: 52618832709246a79a75cb672c0ea8b659602af87c8b4f360e683d75c61e6665
Timestamp: 1716417665 Timestamp [UCT]: 2024-05-22 22:41:05 Age [y:d:h:m:s]: 00:339:17:39:49
Block: 1027855 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 242841 RingCT/type: yes/0
Extra: 0152618832709246a79a75cb672c0ea8b659602af87c8b4f360e683d75c61e666502110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1b0468606f252eba408c2d1ee592291d4ae6b5a171e88aab1c56eb063ff0c076 0.600000000000 1495706 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": 1027865, "vin": [ { "gen": { "height": 1027855 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b0468606f252eba408c2d1ee592291d4ae6b5a171e88aab1c56eb063ff0c076" } } ], "extra": [ 1, 82, 97, 136, 50, 112, 146, 70, 167, 154, 117, 203, 103, 44, 14, 168, 182, 89, 96, 42, 248, 124, 139, 79, 54, 14, 104, 61, 117, 198, 30, 102, 101, 2, 17, 0, 0, 0, 3, 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