Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c5802f1a25652e447d81287ff6b22a005ba315d008dce5737b05d72bc9cbc13

Tx prefix hash: ecccd9b6660599f1b6d6115d872f26c5d84e9f093dc8258f11561f60248169fb
Tx public key: 8b8f1ed44b6d920248e1a7215f88eccd397e69daeb69a1aad962ebaa74b4094c
Timestamp: 1726794564 Timestamp [UCT]: 2024-09-20 01:09:24 Age [y:d:h:m:s]: 00:200:02:16:21
Block: 1113880 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 142819 RingCT/type: yes/0
Extra: 018b8f1ed44b6d920248e1a7215f88eccd397e69daeb69a1aad962ebaa74b4094c021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 85b1c13f55954663de033b01c05af7a61cce8916aa879c20a6a7bcc0bcc544cd 0.600000000000 1593677 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": 1113890, "vin": [ { "gen": { "height": 1113880 } } ], "vout": [ { "amount": 600000000, "target": { "key": "85b1c13f55954663de033b01c05af7a61cce8916aa879c20a6a7bcc0bcc544cd" } } ], "extra": [ 1, 139, 143, 30, 212, 75, 109, 146, 2, 72, 225, 167, 33, 95, 136, 236, 205, 57, 126, 105, 218, 235, 105, 161, 170, 217, 98, 235, 170, 116, 180, 9, 76, 2, 17, 0, 0, 0, 4, 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