Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4be6cfbbb492f115eba6fef3a42751e9815ae037c2f4c6e0465b4193c92a8a2c

Tx prefix hash: cfd30a313b98a3d6d0448f57cb0b51480a0fb039866435e70605609d5dced555
Tx public key: f6ef5cf008a54d6ec4bc8ad33f62146d0b826f1e9599cedb5b677cec509004f0
Timestamp: 1710451930 Timestamp [UCT]: 2024-03-14 21:32:10 Age [y:d:h:m:s]: 01:236:04:18:43
Block: 978415 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 427466 RingCT/type: yes/0
Extra: 01f6ef5cf008a54d6ec4bc8ad33f62146d0b826f1e9599cedb5b677cec509004f002110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 14629b46d371aff08378c28ba27533d0626ae25db259a5242956bc817cc6aae0 0.600000000000 1438442 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": 978425, "vin": [ { "gen": { "height": 978415 } } ], "vout": [ { "amount": 600000000, "target": { "key": "14629b46d371aff08378c28ba27533d0626ae25db259a5242956bc817cc6aae0" } } ], "extra": [ 1, 246, 239, 92, 240, 8, 165, 77, 110, 196, 188, 138, 211, 63, 98, 20, 109, 11, 130, 111, 30, 149, 153, 206, 219, 91, 103, 124, 236, 80, 144, 4, 240, 2, 17, 0, 0, 0, 1, 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