Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 536e8a517f15985c7a1a90ca87e6b03f34433a1ed76c3994c985824f76112ce9

Tx prefix hash: 2c85d46c344a23cca35a0aadcc4588debae481ae6f8eb4b6ffdc05015101ace6
Tx public key: 28b38444a9c7e80487f1563016a7001325ba26312ab22627c34cd0f2b986a0a2
Timestamp: 1728203267 Timestamp [UCT]: 2024-10-06 08:27:47 Age [y:d:h:m:s]: 00:181:12:57:33
Block: 1125570 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 129531 RingCT/type: yes/0
Extra: 0128b38444a9c7e80487f1563016a7001325ba26312ab22627c34cd0f2b986a0a202110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b4424da92b4e247850d47b3dc4d5f7468f82a4ff657a8f9f518c9c5c53c8bb7d 0.600000000000 1608321 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": 1125580, "vin": [ { "gen": { "height": 1125570 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b4424da92b4e247850d47b3dc4d5f7468f82a4ff657a8f9f518c9c5c53c8bb7d" } } ], "extra": [ 1, 40, 179, 132, 68, 169, 199, 232, 4, 135, 241, 86, 48, 22, 167, 0, 19, 37, 186, 38, 49, 42, 178, 38, 39, 195, 76, 208, 242, 185, 134, 160, 162, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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