Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5a45904b1d2baa688e736bacaf090d993570ddffb5e2ea96220083465f48afb7

Tx prefix hash: 028a7997d66d082231cd3ccf395a7e92acd56a394f1fb3088c250554f5949d50
Tx public key: a1d28359150d538c3530d5acd242ab8d1a342ce010183f03d838a68403d05f6c
Timestamp: 1698600173 Timestamp [UCT]: 2023-10-29 17:22:53 Age [y:d:h:m:s]: 01:171:20:14:11
Block: 880355 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 383820 RingCT/type: yes/0
Extra: 01a1d28359150d538c3530d5acd242ab8d1a342ce010183f03d838a68403d05f6c021100000003e6d27f9c000000000000000000

1 output(s) for total of 0.743050694000 dcy

stealth address amount amount idx
00: 1d1a11c626761e96112d102fcb4aee6b6ed389315ae7a099a3f9d1e0819ccfac 0.743050694000 1335911 of 0

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": 880365, "vin": [ { "gen": { "height": 880355 } } ], "vout": [ { "amount": 743050694, "target": { "key": "1d1a11c626761e96112d102fcb4aee6b6ed389315ae7a099a3f9d1e0819ccfac" } } ], "extra": [ 1, 161, 210, 131, 89, 21, 13, 83, 140, 53, 48, 213, 172, 210, 66, 171, 141, 26, 52, 44, 224, 16, 24, 63, 3, 216, 56, 166, 132, 3, 208, 95, 108, 2, 17, 0, 0, 0, 3, 230, 210, 127, 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