Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c50a3fde451c117b09f7e5ca0717d0b98ca8c9c839a1169feef650b029d6c188

Tx prefix hash: 34723f0f6db88660b7a196cf203b8782a0dee490926a594758a9f4f3e89d8d92
Tx public key: da485c55c4ed1404139a647bf119207da6a7acac0c5d1093bc9d7d56c44f3f50
Timestamp: 1733703456 Timestamp [UCT]: 2024-12-09 00:17:36 Age [y:d:h:m:s]: 00:105:19:58:30
Block: 1171077 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 75406 RingCT/type: yes/0
Extra: 01da485c55c4ed1404139a647bf119207da6a7acac0c5d1093bc9d7d56c44f3f50021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 25fc74a3e23c24ea103038ce7ffa777e41a8a862927b1211701bdd43a2346c76 0.600000000000 1656812 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": 1171087, "vin": [ { "gen": { "height": 1171077 } } ], "vout": [ { "amount": 600000000, "target": { "key": "25fc74a3e23c24ea103038ce7ffa777e41a8a862927b1211701bdd43a2346c76" } } ], "extra": [ 1, 218, 72, 92, 85, 196, 237, 20, 4, 19, 154, 100, 123, 241, 25, 32, 125, 166, 167, 172, 172, 12, 93, 16, 147, 188, 157, 125, 86, 196, 79, 63, 80, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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