Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 993e2394d93363bd15e9fa23145e726d4c8540a91e5d7d75ccd0a2d791bd8d30

Tx prefix hash: 5ebaeeb95f877a0461a0229cef58bbcc45a3f905985cced7edc7906e3fcf389e
Tx public key: 96607c01d0f3a437f0e9e702442e44f81b47c588dfe585b7cd46a08744ffa06a
Timestamp: 1694082556 Timestamp [UCT]: 2023-09-07 10:29:16 Age [y:d:h:m:s]: 01:229:06:18:55
Block: 842875 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 424962 RingCT/type: yes/0
Extra: 0196607c01d0f3a437f0e9e702442e44f81b47c588dfe585b7cd46a08744ffa06a02110000000875e3f0e9000000000000000000

1 output(s) for total of 0.989090510000 dcy

stealth address amount amount idx
00: 90127dcf45166a331ec4616edf7466bb820c3cbc47ef3ca1762c67e47a37cb9a 0.989090510000 1296039 of 0

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": 842885, "vin": [ { "gen": { "height": 842875 } } ], "vout": [ { "amount": 989090510, "target": { "key": "90127dcf45166a331ec4616edf7466bb820c3cbc47ef3ca1762c67e47a37cb9a" } } ], "extra": [ 1, 150, 96, 124, 1, 208, 243, 164, 55, 240, 233, 231, 2, 68, 46, 68, 248, 27, 71, 197, 136, 223, 229, 133, 183, 205, 70, 160, 135, 68, 255, 160, 106, 2, 17, 0, 0, 0, 8, 117, 227, 240, 233, 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