Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cecb4ff630a78965355e1a89ba3ea3d3ede52e4ddab5e0f1da26edfdb878082c

Tx prefix hash: 483ee122d1bc42fb5c2ac8511699ce35787950801a2481c7a9218d77475a28c4
Tx public key: 364c8b5b4a37a8aaad117ebb9fa3d3f739f2c59bf3115629aa2bcc775c4e3e40
Timestamp: 1717324471 Timestamp [UCT]: 2024-06-02 10:34:31 Age [y:d:h:m:s]: 00:287:16:24:30
Block: 1035381 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 205594 RingCT/type: yes/0
Extra: 01364c8b5b4a37a8aaad117ebb9fa3d3f739f2c59bf3115629aa2bcc775c4e3e400211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f977f06cce2ff0011ca15b91c50d3a84bc4382f5e92841894a025d7bbc51af1f 0.600000000000 1503902 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": 1035391, "vin": [ { "gen": { "height": 1035381 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f977f06cce2ff0011ca15b91c50d3a84bc4382f5e92841894a025d7bbc51af1f" } } ], "extra": [ 1, 54, 76, 139, 91, 74, 55, 168, 170, 173, 17, 126, 187, 159, 163, 211, 247, 57, 242, 197, 155, 243, 17, 86, 41, 170, 43, 204, 119, 92, 78, 62, 64, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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