Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f60be671aef754c1a5edba0ddc5ad198e01e172cb7f4647bff74328f0fdf1e96

Tx prefix hash: aaaa26b2ef5e8d863bca6ef66ea649795c5a3c7687bd1f531b416d4d4a8afbdf
Tx public key: a12686e8886cfc54aa4ce3798c73dce98c755850ae18601b78a636c26234bd12
Timestamp: 1700680352 Timestamp [UCT]: 2023-11-22 19:12:32 Age [y:d:h:m:s]: 01:351:12:42:41
Block: 897383 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 510132 RingCT/type: yes/0
Extra: 01a12686e8886cfc54aa4ce3798c73dce98c755850ae18601b78a636c26234bd1202110000000133af99f4000000000000000000

1 output(s) for total of 0.652525648000 dcy

stealth address amount amount idx
00: c8e118a807384fc3754d0c617d9cddacdac497838bef366a1b92851d7f1a8619 0.652525648000 1353758 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": 897393, "vin": [ { "gen": { "height": 897383 } } ], "vout": [ { "amount": 652525648, "target": { "key": "c8e118a807384fc3754d0c617d9cddacdac497838bef366a1b92851d7f1a8619" } } ], "extra": [ 1, 161, 38, 134, 232, 136, 108, 252, 84, 170, 76, 227, 121, 140, 115, 220, 233, 140, 117, 88, 80, 174, 24, 96, 27, 120, 166, 54, 194, 98, 52, 189, 18, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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