Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 41f5faac35be168eeab662f59ff532d1a09474d827dec4700868640ecea9b8c6

Tx prefix hash: 20ff773860691b39176b571eb5fc31b9e4720c9606060c936a6511d3051fbaea
Tx public key: 0c72ca7594e02ea50d9e71e6b43dbac1b7ea137101c4c01cf0416d2e6ec910cf
Timestamp: 1735084819 Timestamp [UCT]: 2024-12-25 00:00:19 Age [y:d:h:m:s]: 00:089:02:57:56
Block: 1182499 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 63465 RingCT/type: yes/0
Extra: 010c72ca7594e02ea50d9e71e6b43dbac1b7ea137101c4c01cf0416d2e6ec910cf02110000000a007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2df79cee0337981a14cff2314ba4f9cc8dc6a503a1238cc8c0d048a922ae50ae 0.600000000000 1668934 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": 1182509, "vin": [ { "gen": { "height": 1182499 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2df79cee0337981a14cff2314ba4f9cc8dc6a503a1238cc8c0d048a922ae50ae" } } ], "extra": [ 1, 12, 114, 202, 117, 148, 224, 46, 165, 13, 158, 113, 230, 180, 61, 186, 193, 183, 234, 19, 113, 1, 196, 192, 28, 240, 65, 109, 46, 110, 201, 16, 207, 2, 17, 0, 0, 0, 10, 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