Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 529dfcb6c625dcf983723f8f8311733906e7fd5b608a4a9c9f3f1b2689a54d2a

Tx prefix hash: ffd8d5097a1ccd6e557f6b1cdf27fafa9b2845e0f8c81e1a20db6a281e19fa22
Tx public key: 09ef61b0becffa4bfd4880a28ae151e7803d24d2b07911334a8330221e3265e1
Timestamp: 1627733675 Timestamp [UCT]: 2021-07-31 12:14:35 Age [y:d:h:m:s]: 03:100:09:21:10
Block: 304500 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 844296 RingCT/type: yes/0
Extra: 0109ef61b0becffa4bfd4880a28ae151e7803d24d2b07911334a8330221e3265e102110000003d4a0f5013000000000000000000

1 output(s) for total of 60.128532361000 dcy

stealth address amount amount idx
00: 98092e64e90fea50ea04af887b5366570fe99d9eb9037cc6d4cd2fdbdf6799b1 60.128532361000 635313 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": 304510, "vin": [ { "gen": { "height": 304500 } } ], "vout": [ { "amount": 60128532361, "target": { "key": "98092e64e90fea50ea04af887b5366570fe99d9eb9037cc6d4cd2fdbdf6799b1" } } ], "extra": [ 1, 9, 239, 97, 176, 190, 207, 250, 75, 253, 72, 128, 162, 138, 225, 81, 231, 128, 61, 36, 210, 176, 121, 17, 51, 74, 131, 48, 34, 30, 50, 101, 225, 2, 17, 0, 0, 0, 61, 74, 15, 80, 19, 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