Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ca5cd560a4f0e13f576ec001c963a25d024eaa483d4efd76f4478fc967f0208

Tx prefix hash: 5b4edc84c18af54741f168dcb107e53309d6a39785954eb7229702bc1e4257e2
Tx public key: ff9c539b95ed4a9fae692efb470e8da97ba18f765161e3eea5eee13d7cbf6af3
Timestamp: 1724685579 Timestamp [UCT]: 2024-08-26 15:19:39 Age [y:d:h:m:s]: 00:292:15:41:59
Block: 1096401 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 208965 RingCT/type: yes/0
Extra: 01ff9c539b95ed4a9fae692efb470e8da97ba18f765161e3eea5eee13d7cbf6af3021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 54946c62db0e4b195d1e9c2956693ef550c9a1aa40283a8deda06b0b649e56c4 0.600000000000 1571590 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": 1096411, "vin": [ { "gen": { "height": 1096401 } } ], "vout": [ { "amount": 600000000, "target": { "key": "54946c62db0e4b195d1e9c2956693ef550c9a1aa40283a8deda06b0b649e56c4" } } ], "extra": [ 1, 255, 156, 83, 155, 149, 237, 74, 159, 174, 105, 46, 251, 71, 14, 141, 169, 123, 161, 143, 118, 81, 97, 227, 238, 165, 238, 225, 61, 124, 191, 106, 243, 2, 17, 0, 0, 0, 1, 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