Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ccfe6194605e6db8d93b0002fb7ec33221d5d239f789703c717e920ba80e8f5

Tx prefix hash: 66655f8214e2845973829c7a90934bc93d728349908ba4285e166891ff1184f1
Tx public key: 94f7d316eab4b336e3636b7c9d81a43360b83cb681660631b754ebad3b7ba741
Timestamp: 1709180487 Timestamp [UCT]: 2024-02-29 04:21:27 Age [y:d:h:m:s]: 01:040:17:59:02
Block: 967863 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 290124 RingCT/type: yes/0
Extra: 0194f7d316eab4b336e3636b7c9d81a43360b83cb681660631b754ebad3b7ba7410211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aa8ff5e2348e22da9ed9f7263b0c951f923bec39cdc28228c5e1e0198175d625 0.600000000000 1427654 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": 967873, "vin": [ { "gen": { "height": 967863 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aa8ff5e2348e22da9ed9f7263b0c951f923bec39cdc28228c5e1e0198175d625" } } ], "extra": [ 1, 148, 247, 211, 22, 234, 180, 179, 54, 227, 99, 107, 124, 157, 129, 164, 51, 96, 184, 60, 182, 129, 102, 6, 49, 183, 84, 235, 173, 59, 123, 167, 65, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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