Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 30c3f39ab7d7c05581f25e7be46141b8196be2df1afad211e49dd66a7b945a34

Tx prefix hash: d2ef594dd996609f22cde97754e73a48a274a12b364342012fc0761471c2b851
Tx public key: 00eed76059e45c7f8b0b4cf8aa6d69f851a5d56629921e592d8e8d79dc0a11e4
Timestamp: 1633092620 Timestamp [UCT]: 2021-10-01 12:50:20 Age [y:d:h:m:s]: 03:093:00:11:17
Block: 344479 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 843412 RingCT/type: yes/0
Extra: 0100eed76059e45c7f8b0b4cf8aa6d69f851a5d56629921e592d8e8d79dc0a11e40211000000015410958b000000000000000000

1 output(s) for total of 44.321372376000 dcy

stealth address amount amount idx
00: c82e0bcf47ec54f4f14ac14317cdb2aa9729dd5f71d6da906c35aca4d9b883a5 44.321372376000 706821 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": 344489, "vin": [ { "gen": { "height": 344479 } } ], "vout": [ { "amount": 44321372376, "target": { "key": "c82e0bcf47ec54f4f14ac14317cdb2aa9729dd5f71d6da906c35aca4d9b883a5" } } ], "extra": [ 1, 0, 238, 215, 96, 89, 228, 92, 127, 139, 11, 76, 248, 170, 109, 105, 248, 81, 165, 213, 102, 41, 146, 30, 89, 45, 142, 141, 121, 220, 10, 17, 228, 2, 17, 0, 0, 0, 1, 84, 16, 149, 139, 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