Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b7a900d9fe038326aaa2d4348edaf6aa68e31d82a188c642f9da4be99c4086c5

Tx prefix hash: e6d0842750cbe09b5b09017d6ada2d5aeb562e4a5c47a4370e7ca2fed7ad2cb6
Tx public key: 6d28c28f0918cea852876cc1919de03ba1315fea644d9982e5af782d4caf2f17
Timestamp: 1729942300 Timestamp [UCT]: 2024-10-26 11:31:40 Age [y:d:h:m:s]: 00:200:15:20:41
Block: 1139953 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 143214 RingCT/type: yes/0
Extra: 016d28c28f0918cea852876cc1919de03ba1315fea644d9982e5af782d4caf2f17021100000004a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 014645f7c53a0a57818c0b736a7c1c70c9603de2bae7926f4e85b53d5b0b410e 0.600000000000 1623740 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": 1139963, "vin": [ { "gen": { "height": 1139953 } } ], "vout": [ { "amount": 600000000, "target": { "key": "014645f7c53a0a57818c0b736a7c1c70c9603de2bae7926f4e85b53d5b0b410e" } } ], "extra": [ 1, 109, 40, 194, 143, 9, 24, 206, 168, 82, 135, 108, 193, 145, 157, 224, 59, 161, 49, 95, 234, 100, 77, 153, 130, 229, 175, 120, 45, 76, 175, 47, 23, 2, 17, 0, 0, 0, 4, 161, 29, 186, 152, 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