Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 74e1128051c19470f606daed70418a194f9b4f1fec363b25b8c76a74d0f0560c

Tx prefix hash: a78f21c05e1d7aaffbfa51046b382fb93e27fdd96985f8912a41df00d3fa13db
Tx public key: 7b98b8b6e8243546ae9a335efcdf06560fb5ce041e5a2bdd2e2202f5eb45f1df
Timestamp: 1702539330 Timestamp [UCT]: 2023-12-14 07:35:30 Age [y:d:h:m:s]: 01:108:11:21:35
Block: 912793 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 338663 RingCT/type: yes/0
Extra: 017b98b8b6e8243546ae9a335efcdf06560fb5ce041e5a2bdd2e2202f5eb45f1df021100000007faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 028b6f2037c53fa7f7006a8b704950531f67ce81319e00726b31f608703d0594 0.600000000000 1370029 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": 912803, "vin": [ { "gen": { "height": 912793 } } ], "vout": [ { "amount": 600000000, "target": { "key": "028b6f2037c53fa7f7006a8b704950531f67ce81319e00726b31f608703d0594" } } ], "extra": [ 1, 123, 152, 184, 182, 232, 36, 53, 70, 174, 154, 51, 94, 252, 223, 6, 86, 15, 181, 206, 4, 30, 90, 43, 221, 46, 34, 2, 245, 235, 69, 241, 223, 2, 17, 0, 0, 0, 7, 250, 243, 92, 156, 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