Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 45c61ea77769068c50f0a9c614ff35ad7bdacf46351ea670284a3d5d41da3e99

Tx prefix hash: 742478036bf62b784f9e8aed90cad2e5652e5668bad4e755daa5795defa9497e
Tx public key: e0f33f735490a55d7554df954f9fc9778d0eacd930f26cb5bc71eebaf39fedf5
Timestamp: 1704740824 Timestamp [UCT]: 2024-01-08 19:07:04 Age [y:d:h:m:s]: 01:159:14:41:21
Block: 931039 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 375121 RingCT/type: yes/0
Extra: 01e0f33f735490a55d7554df954f9fc9778d0eacd930f26cb5bc71eebaf39fedf502110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fc138c8ebf4406a9b22c64c1e9279b3e21acf027d80b8dc1a0226a90567d49b5 0.600000000000 1388931 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": 931049, "vin": [ { "gen": { "height": 931039 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fc138c8ebf4406a9b22c64c1e9279b3e21acf027d80b8dc1a0226a90567d49b5" } } ], "extra": [ 1, 224, 243, 63, 115, 84, 144, 165, 93, 117, 84, 223, 149, 79, 159, 201, 119, 141, 14, 172, 217, 48, 242, 108, 181, 188, 113, 238, 186, 243, 159, 237, 245, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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