Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5204549ce12f2940c2e681ceaa0e951b3be95209c75ce427a2a5b5cdd83ed366

Tx prefix hash: 3398e222a61917b3931601d12cf97f4436bef4daa68ce5d4a318fbccc5853e21
Tx public key: 4b0df37997d29a9922edeae9422b1cfa5e0ac64099a91b8b929059101f174b7e
Timestamp: 1734964639 Timestamp [UCT]: 2024-12-23 14:37:19 Age [y:d:h:m:s]: 00:090:12:34:44
Block: 1181529 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 64443 RingCT/type: yes/0
Extra: 014b0df37997d29a9922edeae9422b1cfa5e0ac64099a91b8b929059101f174b7e021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2f1ffb718932d064b9e561a80966151ebbef07a9d99aa10b9ee26d26f1084f6f 0.600000000000 1667954 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": 1181539, "vin": [ { "gen": { "height": 1181529 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f1ffb718932d064b9e561a80966151ebbef07a9d99aa10b9ee26d26f1084f6f" } } ], "extra": [ 1, 75, 13, 243, 121, 151, 210, 154, 153, 34, 237, 234, 233, 66, 43, 28, 250, 94, 10, 198, 64, 153, 169, 27, 139, 146, 144, 89, 16, 31, 23, 75, 126, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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