Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6ff555bda050b8c30597859d2f4fc49ad18e2854baaa392c2aa7a60248e98d4f

Tx prefix hash: dd9e18a2ddfd2275aa5775c0ef11770758c7e7821a79fe76ab58c16a85f3a055
Tx public key: c95c5d3e8131b2ae025df345f8fe8603e085aba03ded85e27341c8b454022d96
Timestamp: 1706278399 Timestamp [UCT]: 2024-01-26 14:13:19 Age [y:d:h:m:s]: 01:141:14:01:37
Block: 943764 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 362233 RingCT/type: yes/0
Extra: 01c95c5d3e8131b2ae025df345f8fe8603e085aba03ded85e27341c8b454022d960211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f3da6e1d0e6fa6041eb41a68300c35489977df5c1fa19e3b856ca079efed3bca 0.600000000000 1401990 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": 943774, "vin": [ { "gen": { "height": 943764 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f3da6e1d0e6fa6041eb41a68300c35489977df5c1fa19e3b856ca079efed3bca" } } ], "extra": [ 1, 201, 92, 93, 62, 129, 49, 178, 174, 2, 93, 243, 69, 248, 254, 134, 3, 224, 133, 171, 160, 61, 237, 133, 226, 115, 65, 200, 180, 84, 2, 45, 150, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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