Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ca8474fc0a5a59de525d40364bdf2217fec09efa1d6bda0c83d6860c40888472

Tx prefix hash: bb21bbb3840da143cef7e8f81008a2020ccf704c628a8b9dcf14b77137e0cdb7
Tx public key: 1f4304b70b6f78d7c6c5edb0090c72c34cb23e46533af23d4fea2b87c2b497ff
Timestamp: 1658787109 Timestamp [UCT]: 2022-07-25 22:11:49 Age [y:d:h:m:s]: 02:169:15:36:38
Block: 551695 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 642653 RingCT/type: yes/0
Extra: 011f4304b70b6f78d7c6c5edb0090c72c34cb23e46533af23d4fea2b87c2b497ff02110000000275e3f0e9000000000000000000

1 output(s) for total of 9.120315475000 dcy

stealth address amount amount idx
00: aa77a64ab0aef7ab2eba491e5511e733b50d06e04aa15b8a36a34ebd10aacfd8 9.120315475000 983337 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": 551705, "vin": [ { "gen": { "height": 551695 } } ], "vout": [ { "amount": 9120315475, "target": { "key": "aa77a64ab0aef7ab2eba491e5511e733b50d06e04aa15b8a36a34ebd10aacfd8" } } ], "extra": [ 1, 31, 67, 4, 183, 11, 111, 120, 215, 198, 197, 237, 176, 9, 12, 114, 195, 76, 178, 62, 70, 83, 58, 242, 61, 79, 234, 43, 135, 194, 180, 151, 255, 2, 17, 0, 0, 0, 2, 117, 227, 240, 233, 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