Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 99528bee2506edf76b4cd0006d23f4dd14f35ded1edcf3941767a9ef4ac3506d

Tx prefix hash: a51c672570dada2d6294fb4d6f4c080c24f962fd2722918e5f58d7f5cbc62c4c
Tx public key: 16349d1d13d10b7893e1ae553df7cd298a36734b46f67492aa19a48fff69b282
Timestamp: 1725312661 Timestamp [UCT]: 2024-09-02 21:31:01 Age [y:d:h:m:s]: 00:129:08:09:43
Block: 1101604 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 92501 RingCT/type: yes/0
Extra: 0116349d1d13d10b7893e1ae553df7cd298a36734b46f67492aa19a48fff69b282021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d36f2e98e9841a8d8c85bbf99392086aafc11a86bd641fb317202f70f346146f 0.600000000000 1577715 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": 1101614, "vin": [ { "gen": { "height": 1101604 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d36f2e98e9841a8d8c85bbf99392086aafc11a86bd641fb317202f70f346146f" } } ], "extra": [ 1, 22, 52, 157, 29, 19, 209, 11, 120, 147, 225, 174, 85, 61, 247, 205, 41, 138, 54, 115, 75, 70, 246, 116, 146, 170, 25, 164, 143, 255, 105, 178, 130, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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