Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fad6dd839b62e25d78026b058d62ff2fe4180b3cc52fe47004e78152ea3ee954

Tx prefix hash: c2d9d33faf8b3a4454e769a3641172e82b303d1553caf511c93b47ddea79a01f
Tx public key: 7234f30cd49827bfe8eb8b04b993fa9bac4c78bd24eb57c457d1a65bea461693
Timestamp: 1727946943 Timestamp [UCT]: 2024-10-03 09:15:43 Age [y:d:h:m:s]: 00:207:16:14:43
Block: 1123436 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 148252 RingCT/type: yes/0
Extra: 017234f30cd49827bfe8eb8b04b993fa9bac4c78bd24eb57c457d1a65bea461693021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 35e699856e0d6ab7f463632f43a216d1d89b94bc8e65f513b7bbf399adb9a1ae 0.600000000000 1605971 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": 1123446, "vin": [ { "gen": { "height": 1123436 } } ], "vout": [ { "amount": 600000000, "target": { "key": "35e699856e0d6ab7f463632f43a216d1d89b94bc8e65f513b7bbf399adb9a1ae" } } ], "extra": [ 1, 114, 52, 243, 12, 212, 152, 39, 191, 232, 235, 139, 4, 185, 147, 250, 155, 172, 76, 120, 189, 36, 235, 87, 196, 87, 209, 166, 91, 234, 70, 22, 147, 2, 17, 0, 0, 0, 3, 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