Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cfe60a6612b302f22569f56c7c512a9023dae512e8658c930fb191834de7d3d2

Tx prefix hash: 2030a28a7d8c903cf9d0d6bc228538feddde2aad7ca764a0dfc233fce0e5021d
Tx public key: 1985566491c7ea6b1494e6bbe78a09ded6d0bc677b7b6f334b954a68752357e4
Timestamp: 1697408479 Timestamp [UCT]: 2023-10-15 22:21:19 Age [y:d:h:m:s]: 01:108:14:16:50
Block: 870465 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 338607 RingCT/type: yes/0
Extra: 011985566491c7ea6b1494e6bbe78a09ded6d0bc677b7b6f334b954a68752357e40211000000014b8f5122000000000000000000

1 output(s) for total of 0.801287069000 dcy

stealth address amount amount idx
00: 9cf0cc0b5923d80d1a7452b5c127036badb5598c5ce87308d0df315e3475a82e 0.801287069000 1325344 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": 870475, "vin": [ { "gen": { "height": 870465 } } ], "vout": [ { "amount": 801287069, "target": { "key": "9cf0cc0b5923d80d1a7452b5c127036badb5598c5ce87308d0df315e3475a82e" } } ], "extra": [ 1, 25, 133, 86, 100, 145, 199, 234, 107, 20, 148, 230, 187, 231, 138, 9, 222, 214, 208, 188, 103, 123, 123, 111, 51, 75, 149, 74, 104, 117, 35, 87, 228, 2, 17, 0, 0, 0, 1, 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