Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 68d6317bfc4416829fe6ae6a2e91de0b48d619e2d1652ecb4dda03819b77a3e6

Tx prefix hash: fcca605e0ff8ada8183fe8684f4d99a9a5f3347d2ca7e03261cedfd97ca5c0e0
Tx public key: 3230a5563487d5cdfd676aec0a1982857b8337f5ce294a69d880c7c9403092e8
Timestamp: 1719299646 Timestamp [UCT]: 2024-06-25 07:14:06 Age [y:d:h:m:s]: 01:134:20:17:09
Block: 1051742 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 354913 RingCT/type: yes/0
Extra: 013230a5563487d5cdfd676aec0a1982857b8337f5ce294a69d880c7c9403092e802110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 475c383e0150d4aa8a9729f596dfa5b23e90ee4a400590bc30149dc39c35c457 0.600000000000 1522061 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": 1051752, "vin": [ { "gen": { "height": 1051742 } } ], "vout": [ { "amount": 600000000, "target": { "key": "475c383e0150d4aa8a9729f596dfa5b23e90ee4a400590bc30149dc39c35c457" } } ], "extra": [ 1, 50, 48, 165, 86, 52, 135, 213, 205, 253, 103, 106, 236, 10, 25, 130, 133, 123, 131, 55, 245, 206, 41, 74, 105, 216, 128, 199, 201, 64, 48, 146, 232, 2, 17, 0, 0, 0, 1, 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