Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a4d8c61aadacc18b631bd804b8a6c566dce9e214c9667d1f5c4b7040ac7ad5af

Tx prefix hash: 023673302ecc7774bae579012989129ea3d45563111dd51abf20295727d57b2d
Tx public key: 2e017725f8e4036065d1ea3152bfb90a829b5198fd62ad0d5aa1de64ac0953e1
Timestamp: 1709010130 Timestamp [UCT]: 2024-02-27 05:02:10 Age [y:d:h:m:s]: 01:030:07:23:43
Block: 966449 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 282670 RingCT/type: yes/0
Extra: 012e017725f8e4036065d1ea3152bfb90a829b5198fd62ad0d5aa1de64ac0953e102110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1eebd00ebf3faf5daf64143538cd5305cfed7aaee40ee38f19a2ef8eb7bcf1e5 0.600000000000 1426206 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": 966459, "vin": [ { "gen": { "height": 966449 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1eebd00ebf3faf5daf64143538cd5305cfed7aaee40ee38f19a2ef8eb7bcf1e5" } } ], "extra": [ 1, 46, 1, 119, 37, 248, 228, 3, 96, 101, 209, 234, 49, 82, 191, 185, 10, 130, 155, 81, 152, 253, 98, 173, 13, 90, 161, 222, 100, 172, 9, 83, 225, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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