Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 442d7c5bd338d3c84f9eb856eea08c2e1b11483eb6fcc993880d96bbb70ce4d8

Tx prefix hash: 27a736e2fcbe9505c40a3dcc703c038cc2d68844388b61877128cfa304600a89
Tx public key: bbaa7172dfbf44a27919bb735e025a9f5db227ebdf8884ac5178d4a38fb6b402
Timestamp: 1723874648 Timestamp [UCT]: 2024-08-17 06:04:08 Age [y:d:h:m:s]: 01:081:20:09:21
Block: 1089684 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 316934 RingCT/type: yes/0
Extra: 01bbaa7172dfbf44a27919bb735e025a9f5db227ebdf8884ac5178d4a38fb6b402021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f2227ae0eca1e8fc8ec70a2ec159b18e8a8b3bea9462cc209da70125e770fa9 0.600000000000 1564307 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": 1089694, "vin": [ { "gen": { "height": 1089684 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f2227ae0eca1e8fc8ec70a2ec159b18e8a8b3bea9462cc209da70125e770fa9" } } ], "extra": [ 1, 187, 170, 113, 114, 223, 191, 68, 162, 121, 25, 187, 115, 94, 2, 90, 159, 93, 178, 39, 235, 223, 136, 132, 172, 81, 120, 212, 163, 143, 182, 180, 2, 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