Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d0e24a40a4bdfca95024582c460dadbfebaac0cbc97ea85952c3750a911db921

Tx prefix hash: 5152d64d3c8318a1dd725422587e3addd41fc9201b7f5600c49453e54670c5e1
Tx public key: 0ae2c8f40340cb64e8a97197f742793b65d158ce533c574613b3bfa84562bdf4
Timestamp: 1706004747 Timestamp [UCT]: 2024-01-23 10:12:27 Age [y:d:h:m:s]: 01:144:21:36:12
Block: 941506 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 364592 RingCT/type: yes/0
Extra: 010ae2c8f40340cb64e8a97197f742793b65d158ce533c574613b3bfa84562bdf402110000000e59dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8619f69eb237a0abe359c94512fb36d68c2a1bd3880499de32c8c259acb4bd52 0.600000000000 1399656 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": 941516, "vin": [ { "gen": { "height": 941506 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8619f69eb237a0abe359c94512fb36d68c2a1bd3880499de32c8c259acb4bd52" } } ], "extra": [ 1, 10, 226, 200, 244, 3, 64, 203, 100, 232, 169, 113, 151, 247, 66, 121, 59, 101, 209, 88, 206, 83, 60, 87, 70, 19, 179, 191, 168, 69, 98, 189, 244, 2, 17, 0, 0, 0, 14, 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