Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0cfa3af6e59f63c2afb3b54eaf8951e2ad3f9ef8a7d44fe90d91153c6a954a2c

Tx prefix hash: cee5329ca483627a14ddb709c8e9059cdb91a237cf62483f613a283c89c00fc1
Tx public key: bba22a5e42ce76f2f687851ccc1c617d3f124a1d46175847371bdb36607c8aa0
Timestamp: 1695323173 Timestamp [UCT]: 2023-09-21 19:06:13 Age [y:d:h:m:s]: 01:214:02:02:09
Block: 853168 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 414081 RingCT/type: yes/0
Extra: 01bba22a5e42ce76f2f687851ccc1c617d3f124a1d46175847371bdb36607c8aa00211000000074b8f5122000000000000000000

1 output(s) for total of 0.914324382000 dcy

stealth address amount amount idx
00: f8a63732930b7e3ca5f6e4f15c46a71aa10611d9b03fe8d4ddbcfe961f84e0f9 0.914324382000 1307052 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": 853178, "vin": [ { "gen": { "height": 853168 } } ], "vout": [ { "amount": 914324382, "target": { "key": "f8a63732930b7e3ca5f6e4f15c46a71aa10611d9b03fe8d4ddbcfe961f84e0f9" } } ], "extra": [ 1, 187, 162, 42, 94, 66, 206, 118, 242, 246, 135, 133, 28, 204, 28, 97, 125, 63, 18, 74, 29, 70, 23, 88, 71, 55, 27, 219, 54, 96, 124, 138, 160, 2, 17, 0, 0, 0, 7, 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