Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba7de733b428c4248a332fbf9bad505aea912225d3ee33b6a8af1d6e509bc926

Tx prefix hash: 5ddb97a4b63378c31a717fa607b2c3b86f14d6c44bbeca83103c823811c8d0df
Tx public key: 0a33c4fa8be165b53c385e3b60d628fdcdf4cdb237892620e4ce970e71352ed4
Timestamp: 1737910088 Timestamp [UCT]: 2025-01-26 16:48:08 Age [y:d:h:m:s]: 00:145:19:02:13
Block: 1205867 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103864 RingCT/type: yes/0
Extra: 010a33c4fa8be165b53c385e3b60d628fdcdf4cdb237892620e4ce970e71352ed4021100000005e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f14944f70e816a66c2ca969cede5adf6e74c6c3276daf66c162326a7011a9e07 0.600000000000 1692566 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": 1205877, "vin": [ { "gen": { "height": 1205867 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f14944f70e816a66c2ca969cede5adf6e74c6c3276daf66c162326a7011a9e07" } } ], "extra": [ 1, 10, 51, 196, 250, 139, 225, 101, 181, 60, 56, 94, 59, 96, 214, 40, 253, 205, 244, 205, 178, 55, 137, 38, 32, 228, 206, 151, 14, 113, 53, 46, 212, 2, 17, 0, 0, 0, 5, 228, 220, 144, 9, 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