Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bac98a52c6cb1889b4fae843deba9c1d76c9f4447c01dd441f6b4dfadbc8e2df

Tx prefix hash: ef5b222b12fc4f351f5a19994104fb4a60950bd6bc3dc59dbb3bb6866edda56d
Tx public key: 7a25f479bf3c38cd9ca110b5eef661c453ae82c92ac38bdc5f43880554814af8
Timestamp: 1694873766 Timestamp [UCT]: 2023-09-16 14:16:06 Age [y:d:h:m:s]: 01:202:10:47:56
Block: 849430 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 405777 RingCT/type: yes/0
Extra: 017a25f479bf3c38cd9ca110b5eef661c453ae82c92ac38bdc5f43880554814af80211000000034b8f5122000000000000000000

1 output(s) for total of 0.940775183000 dcy

stealth address amount amount idx
00: 0cde20599c55eb4d5d3f5f68179d7ba04394a71efb990ac4d79d973a0f05c2dd 0.940775183000 1303096 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": 849440, "vin": [ { "gen": { "height": 849430 } } ], "vout": [ { "amount": 940775183, "target": { "key": "0cde20599c55eb4d5d3f5f68179d7ba04394a71efb990ac4d79d973a0f05c2dd" } } ], "extra": [ 1, 122, 37, 244, 121, 191, 60, 56, 205, 156, 161, 16, 181, 238, 246, 97, 196, 83, 174, 130, 201, 42, 195, 139, 220, 95, 67, 136, 5, 84, 129, 74, 248, 2, 17, 0, 0, 0, 3, 75, 143, 81, 34, 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