Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f31278ec36f356e748342fad0fa30d8bd866d577e3f5fe828ba5f28a9efdd6f

Tx prefix hash: f11eac814da5d28c8fe0299fadc169593d940caa42dabd921a5ff9d2fb11cb1c
Tx public key: 823397a08be50270d3b9f0112f41aaa997a924cb9cf7b2abb3d9b33c7e710ad0
Timestamp: 1733043174 Timestamp [UCT]: 2024-12-01 08:52:54 Age [y:d:h:m:s]: 00:113:14:16:06
Block: 1165598 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80968 RingCT/type: yes/0
Extra: 01823397a08be50270d3b9f0112f41aaa997a924cb9cf7b2abb3d9b33c7e710ad00211000000081f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7b2b4afe434a3b57003fa25594c8d1617643fef02aeb248e738fe6619228e2d1 0.600000000000 1651273 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": 1165608, "vin": [ { "gen": { "height": 1165598 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7b2b4afe434a3b57003fa25594c8d1617643fef02aeb248e738fe6619228e2d1" } } ], "extra": [ 1, 130, 51, 151, 160, 139, 229, 2, 112, 211, 185, 240, 17, 47, 65, 170, 169, 151, 169, 36, 203, 156, 247, 178, 171, 179, 217, 179, 60, 126, 113, 10, 208, 2, 17, 0, 0, 0, 8, 31, 10, 83, 235, 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