Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8a3807de14a30d9396b693f155be586e790d8cd207df1ff925521097bedf54f7

Tx prefix hash: 8144fba3d2260792c7beaed32ff792073a369359bb6fff8fb0aae299d99d5f6c
Tx public key: f9c77dd4b87e9609e19841d3f563d8a7110d407e5251ac74d885aad7e50145b0
Timestamp: 1730175539 Timestamp [UCT]: 2024-10-29 04:18:59 Age [y:d:h:m:s]: 00:144:08:04:31
Block: 1141864 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102965 RingCT/type: yes/0
Extra: 01f9c77dd4b87e9609e19841d3f563d8a7110d407e5251ac74d885aad7e50145b002110000000225a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7c58d5bb212e3b75aaa48e7b8a0856eaf69195e18dcd7a097a19c0bb42b490b1 0.600000000000 1625695 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": 1141874, "vin": [ { "gen": { "height": 1141864 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7c58d5bb212e3b75aaa48e7b8a0856eaf69195e18dcd7a097a19c0bb42b490b1" } } ], "extra": [ 1, 249, 199, 125, 212, 184, 126, 150, 9, 225, 152, 65, 211, 245, 99, 216, 167, 17, 13, 64, 126, 82, 81, 172, 116, 216, 133, 170, 215, 229, 1, 69, 176, 2, 17, 0, 0, 0, 2, 37, 163, 90, 15, 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