Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 353494003959ccdee5cd7acb5870b37b6f0933b0dbe59457e30b5217df43e61c

Tx prefix hash: fe4c50c7c1d8146713954ef5a37a0d153ed099a3ccaf1cf47630c5def0c18c59
Tx public key: 6bcdfdcc4de9dc7b47974b0f3df1b072f11ef727b19d407871991fbf74fbe961
Timestamp: 1718472123 Timestamp [UCT]: 2024-06-15 17:22:03 Age [y:d:h:m:s]: 00:277:18:34:56
Block: 1044903 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 198501 RingCT/type: yes/0
Extra: 016bcdfdcc4de9dc7b47974b0f3df1b072f11ef727b19d407871991fbf74fbe961021100000001b27e313d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e7d5003c62bd1fefd77852a798712107aa689aebdc9e62777b68bd4ad0c9564 0.600000000000 1514336 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": 1044913, "vin": [ { "gen": { "height": 1044903 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e7d5003c62bd1fefd77852a798712107aa689aebdc9e62777b68bd4ad0c9564" } } ], "extra": [ 1, 107, 205, 253, 204, 77, 233, 220, 123, 71, 151, 75, 15, 61, 241, 176, 114, 241, 30, 247, 39, 177, 157, 64, 120, 113, 153, 31, 191, 116, 251, 233, 97, 2, 17, 0, 0, 0, 1, 178, 126, 49, 61, 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