Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 22d74ccf7ce2dddf976ff5279f6d2e7c016bd852d80eae04f9d56814e0dce666

Tx prefix hash: 7292994273fbe30d041a7e671deca88cd3a2f6859e10d249cfc0eaa8a67844d1
Tx public key: f9b82aa65379e339b63cdbff317c695a7fc9477cba1bae2162092b3878cc1861
Timestamp: 1708733506 Timestamp [UCT]: 2024-02-24 00:11:46 Age [y:d:h:m:s]: 01:033:10:49:46
Block: 964151 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 284923 RingCT/type: yes/0
Extra: 01f9b82aa65379e339b63cdbff317c695a7fc9477cba1bae2162092b3878cc186102110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 36685ef07c9b750ff9a66a31dfe2dca854c679fdb0c545caa6a25e3676c0b364 0.600000000000 1423878 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": 964161, "vin": [ { "gen": { "height": 964151 } } ], "vout": [ { "amount": 600000000, "target": { "key": "36685ef07c9b750ff9a66a31dfe2dca854c679fdb0c545caa6a25e3676c0b364" } } ], "extra": [ 1, 249, 184, 42, 166, 83, 121, 227, 57, 182, 60, 219, 255, 49, 124, 105, 90, 127, 201, 71, 124, 186, 27, 174, 33, 98, 9, 43, 56, 120, 204, 24, 97, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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