Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9285ac5ac59d40eaf8d1ab519a27d2596a672abdf9a2a154e4c936333552189d

Tx prefix hash: 54d5331fdb8216e1b3a21542bb15c170a57a8ca1de43a0bbc435397d00063762
Tx public key: 6f9fe01b451519424f43aa3408a9bbd5e989277cef4e5e416dbb19c056517cb9
Timestamp: 1736368048 Timestamp [UCT]: 2025-01-08 20:27:28 Age [y:d:h:m:s]: 00:064:19:26:04
Block: 1193116 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 46114 RingCT/type: yes/0
Extra: 016f9fe01b451519424f43aa3408a9bbd5e989277cef4e5e416dbb19c056517cb9021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0a70a366fa239f7ed920842c42dfd2ad9a4f25f10aed9560c59d723e4b7879f2 0.600000000000 1679675 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": 1193126, "vin": [ { "gen": { "height": 1193116 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a70a366fa239f7ed920842c42dfd2ad9a4f25f10aed9560c59d723e4b7879f2" } } ], "extra": [ 1, 111, 159, 224, 27, 69, 21, 25, 66, 79, 67, 170, 52, 8, 169, 187, 213, 233, 137, 39, 124, 239, 78, 94, 65, 109, 187, 25, 192, 86, 81, 124, 185, 2, 17, 0, 0, 0, 3, 0, 127, 151, 138, 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