Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6de5ce4862f620facbaed6192d2694543223abff02964fb9aa5a5849cc93d8bb

Tx prefix hash: 7017ffc04ea71e6906b6e7bfdbbb81f804f7cbb30ee02dbaa215f83820112809
Tx public key: 1e1d8ea4a4e3102f3693b2cb50b581a9b14206abcf42114936121f627f5d63c8
Timestamp: 1713944300 Timestamp [UCT]: 2024-04-24 07:38:20 Age [y:d:h:m:s]: 01:223:19:46:01
Block: 1007351 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 418641 RingCT/type: yes/0
Extra: 011e1d8ea4a4e3102f3693b2cb50b581a9b14206abcf42114936121f627f5d63c80211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 258409556d9211d3448665cd1d9956329141842a0eaf90b04eb9147b3dad5a53 0.600000000000 1468665 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": 1007361, "vin": [ { "gen": { "height": 1007351 } } ], "vout": [ { "amount": 600000000, "target": { "key": "258409556d9211d3448665cd1d9956329141842a0eaf90b04eb9147b3dad5a53" } } ], "extra": [ 1, 30, 29, 142, 164, 164, 227, 16, 47, 54, 147, 178, 203, 80, 181, 129, 169, 177, 66, 6, 171, 207, 66, 17, 73, 54, 18, 31, 98, 127, 93, 99, 200, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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