Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 399cdbe27ce3c00851a3b3beca57d0ca0bacb82ea7232b9e515473f1dcde0bc6

Tx prefix hash: 0210e6be363b55c1c2f42f31fb1455fdd187fd8810c98ffe86e01e7900d32711
Tx public key: afe7302deb81d2ebcf8403dddb903f74b46117622a6b763a039c13bf5c421102
Timestamp: 1727942266 Timestamp [UCT]: 2024-10-03 07:57:46 Age [y:d:h:m:s]: 01:038:09:23:59
Block: 1123405 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 285816 RingCT/type: yes/0
Extra: 01afe7302deb81d2ebcf8403dddb903f74b46117622a6b763a039c13bf5c421102021100000009e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 439e1e8ccda59b98299e329fd5b1b3c88b82110f54ef7290ea16f6f91619aeb8 0.600000000000 1605938 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": 1123415, "vin": [ { "gen": { "height": 1123405 } } ], "vout": [ { "amount": 600000000, "target": { "key": "439e1e8ccda59b98299e329fd5b1b3c88b82110f54ef7290ea16f6f91619aeb8" } } ], "extra": [ 1, 175, 231, 48, 45, 235, 129, 210, 235, 207, 132, 3, 221, 219, 144, 63, 116, 180, 97, 23, 98, 42, 107, 118, 58, 3, 156, 19, 191, 92, 66, 17, 2, 2, 17, 0, 0, 0, 9, 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