Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d6838f51eb1b45af766236df23811eb584140b3d737ea0101fdfdb6682a2614a

Tx prefix hash: 84ac57da91803db13b1de8da6aa9126a2d0c0b78502a80d34ec8fb7336431c53
Tx public key: 5968c2d66650b6028a02e515ac3c1bd0fb70f09aca1c228eb2bf6068d6bcf597
Timestamp: 1748285507 Timestamp [UCT]: 2025-05-26 18:51:47 Age [y:d:h:m:s]: 00:192:09:34:37
Block: 1291519 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 135232 RingCT/type: yes/0
Extra: 015968c2d66650b6028a02e515ac3c1bd0fb70f09aca1c228eb2bf6068d6bcf5970211000000081f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e3e3e47b70668cf3d75de0f88780903a9e7f975c3964b7c5224f8d42c64c5b75 0.600000000000 1778990 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": 1291529, "vin": [ { "gen": { "height": 1291519 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e3e3e47b70668cf3d75de0f88780903a9e7f975c3964b7c5224f8d42c64c5b75" } } ], "extra": [ 1, 89, 104, 194, 214, 102, 80, 182, 2, 138, 2, 229, 21, 172, 60, 27, 208, 251, 112, 240, 154, 202, 28, 34, 142, 178, 191, 96, 104, 214, 188, 245, 151, 2, 17, 0, 0, 0, 8, 31, 144, 81, 122, 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