Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d919b77557f36fab2dccc4381b3495bef3764e888a03370a20046cfe879fef4

Tx prefix hash: 3c1eb33a93268c936c0a380df71c277a22ff7d29d82edaf912ad654aa23dafae
Tx public key: 2240ae95fdb3ebe3a966fb219f441286e88c60433c1bd580ea476be5bbaf42a4
Timestamp: 1716727357 Timestamp [UCT]: 2024-05-26 12:42:37 Age [y:d:h:m:s]: 01:171:07:06:05
Block: 1030432 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 381006 RingCT/type: yes/0
Extra: 012240ae95fdb3ebe3a966fb219f441286e88c60433c1bd580ea476be5bbaf42a40211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b107c592b3bf11a0243fd09fa9573aada000ac6b2d9ebe15e94ea013e2dd4df 0.600000000000 1498687 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": 1030442, "vin": [ { "gen": { "height": 1030432 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b107c592b3bf11a0243fd09fa9573aada000ac6b2d9ebe15e94ea013e2dd4df" } } ], "extra": [ 1, 34, 64, 174, 149, 253, 179, 235, 227, 169, 102, 251, 33, 159, 68, 18, 134, 232, 140, 96, 67, 60, 27, 213, 128, 234, 71, 107, 229, 187, 175, 66, 164, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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