Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 569aa97bbc31de997032b0e4dc7c2e4403dfc21ef98fc4179b2b955ade55b916

Tx prefix hash: c4f117433600849afebdbcfc4f08b2e28755270cc36b60ee49da555dcf304d08
Tx public key: c3f3534e628c956b55c04f5dbf3d56775175aba3f0e3af1bf84f7c21f0a51647
Timestamp: 1706970288 Timestamp [UCT]: 2024-02-03 14:24:48 Age [y:d:h:m:s]: 00:347:08:33:10
Block: 949517 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 248674 RingCT/type: yes/0
Extra: 01c3f3534e628c956b55c04f5dbf3d56775175aba3f0e3af1bf84f7c21f0a5164702110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 53f18af0520d2dd52d2f18c3d38f4c75189b2824681d6f5c0851a09cde515357 0.600000000000 1408043 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": 949527, "vin": [ { "gen": { "height": 949517 } } ], "vout": [ { "amount": 600000000, "target": { "key": "53f18af0520d2dd52d2f18c3d38f4c75189b2824681d6f5c0851a09cde515357" } } ], "extra": [ 1, 195, 243, 83, 78, 98, 140, 149, 107, 85, 192, 79, 93, 191, 61, 86, 119, 81, 117, 171, 163, 240, 227, 175, 27, 248, 79, 124, 33, 240, 165, 22, 71, 2, 17, 0, 0, 0, 4, 89, 218, 211, 245, 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