Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af35e825ac88607f0f3ae8ef86f6bd16a0d2ce7b290239dfdb9d01a0bbca9fa0

Tx prefix hash: fc0c994a948fb32080a0ce2a6381b73a8735d80f03ab9eb833bcc7a3b867dd1a
Tx public key: 38b5696bf4b94b80fa1e6db73c2bf636f994a193ec2c47b2835fe5fb50eda002
Timestamp: 1577816342 Timestamp [UCT]: 2019-12-31 18:19:02 Age [y:d:h:m:s]: 05:133:10:43:43
Block: 35932 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1245147 RingCT/type: yes/0
Extra: 0138b5696bf4b94b80fa1e6db73c2bf636f994a193ec2c47b2835fe5fb50eda002021100000032398c17aa000000000000000000

1 output(s) for total of 466.598374514000 dcy

stealth address amount amount idx
00: 948b751da02760dcbc9a3c5f711092cb3072b4d5a9b670eef1e0ec952b23c441 466.598374514000 60702 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": 35942, "vin": [ { "gen": { "height": 35932 } } ], "vout": [ { "amount": 466598374514, "target": { "key": "948b751da02760dcbc9a3c5f711092cb3072b4d5a9b670eef1e0ec952b23c441" } } ], "extra": [ 1, 56, 181, 105, 107, 244, 185, 75, 128, 250, 30, 109, 183, 60, 43, 246, 54, 249, 148, 161, 147, 236, 44, 71, 178, 131, 95, 229, 251, 80, 237, 160, 2, 2, 17, 0, 0, 0, 50, 57, 140, 23, 170, 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